-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: 0.11.0 release note #491
Conversation
Signed-off-by: he1pa <[email protected]>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Signed-off-by: he1pa <[email protected]>
Signed-off-by: zongz <[email protected]>
Signed-off-by: zongz <[email protected]>
|
||
#### Standard Libraries | ||
|
||
- KCL new standard libraries `filesha512` 和 `fileblake3`。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo
![hint](/img/blog/2024-12-06-kcl-0.11.0-release/hint.png) | ||
- IDE schema hover 中提供了 attr 默认值信息。 | ||
![hover](/img/blog/2024-12-06-kcl-0.11.0-release/hover.png) | ||
- IDE 能够监控工作目录中的配置文件变化,在 kpm 更新依赖后能自动更新 IDE 中的语义信息 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete
![hint](/img/blog/2024-12-06-kcl-0.11.0-release/hint.png) | ||
- IDE hover provides schema attribute default value information. | ||
![hover](/img/blog/2024-12-06-kcl-0.11.0-release/hover.png) | ||
- IDE can watch changes in configuration files(kcl.mod) in the workspace, and automatically update the semantic information in the IDE after kpm updates dependencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete
Signed-off-by: zongz <[email protected]>
Signed-off-by: zongz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: